home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group93b.txt
/
000116_icon-group-sender _Fri May 21 22:17:24 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1993-06-16
|
1KB
Received: from owl.CS.Arizona.EDU by cheltenham.CS.Arizona.EDU; Wed, 26 May 1993 12:26:56 MST
Received: by owl.cs.arizona.edu; Wed, 26 May 1993 12:26:56 MST
Date: 21 May 93 22:17:24 GMT
From: portal!cup.portal.com!Eric-Amick@uunet.uu.net (Richard E Amick)
Organization: The Portal System (TM)
Subject: Re: Icon on a mixed-architecture network
Message-Id: <81825@cup.portal.com>
References: <1993May20.134500.4321@mlfarm.com>
Sender: icon-group-request@cs.arizona.edu
To: icon-group@cs.arizona.edu
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
>We build Icon programs here with the space-saving Unix header
>
> #! /usr/local/bin/iconx
>
>at the top of the executable files. This makes for speedy and compact
>executables, but ignores the ICONX environment variable. Assuming
>machines on the network have the appropriate Sun3 or Sun4 iconx on
>their PATH, will the same executable run on either system? I don't
>think there are any byte-swapping nasties between Sun3 and Sun4
>architectures.
Another possibility is to change the Unix header to
exec "${ICONX-iconx}" "$0" "$@"
which will use the ICONX variable if it's defined, otherwise it searches
the path.